@stationeros Thank you raising for the PR 👍 . Few points as per the design of status behaviour:

• Remote url attached to a deprecated server is a valid URL. Deprecated server can still be an active server for downstream clients. It might not be maintained by the owner. If a user wants to publish a new package with this remote url, they have to mark this as deleted first.
• Migrating from deleted to active and vice versa are the 2 status that require remote url validation.
• If we are updating a server then also we have to check for remote url validation.

@stationeros We might not need this change, except for test cases. As this behaviour is already part of code where the default value is to exclude deleted servers. If you will run the test cases without the filter change, you will notice that tests are passing.

Reason for the issue is different where status of servers are not marked as deleted. Apologies from my end, I missed checking the default values first. But we might need test cases though. I appreciate your contribution and patience here.

@stationeros We might not need this change, except for test cases. As this behaviour is already part of code where the default value is to exclude deleted servers. If you will run the test cases without the filter change, you will notice that tests are passing.

Reason for the issue is different where status of servers are not marked as deleted. Apologies from my end, I missed checking the default values first. But we might need test cases though. I appreciate your contribution and patience here.

nvm - reverted the logic and kept the TCs if that helps